Media vaulting

ABSTRACT

A method is disclosed that comprises creating a plurality of vaulting policies, each vaulting policy having one or more cycles specifying a movement of media to a destination location and a time to execute the cycle. The method further comprises associating a first vaulting policy of the plurality to a first set of media and associating a second vaulting policy of the plurality to a second set of media, the second set of media comprising a subset of the first set of media, the second vaulting policy superseding the first vaulting policy for the media contained in the subset.

BACKGROUND OF THE INVENTION

The protection of data has become a high priority item for mostbusinesses. In the event of a disaster, companies must be able to accessdata in a timely fashion or business may grind to a halt. Additionally,companies must safeguard their data in order to comply with regulationsrelating to the protection of customer data. Thus, companies are makingsizeable investments on data protection and data protection strategies.

A great deal of consideration is given as to what data to protect, whereto store protected data, and how long data should be protected. Mediacontaining protected data may be stored in backup devices, onsitevaults, or offsite. Administrators may need to manually keep track ofwhere the media is stored. Alternately, media vaulting managementsoftware may be used to track limited movement of media.

Currently, vaulting management software only allows very basic vaultingpolicies to be set up. These policies are typically not able to fulfillthe requirements for complex media vaulting schemes with multiple mediamovements. Additionally, the current software also does not provide theability for an administrator to confirm that media reached the intendeddestination.

Another problem is the notification of offsite vendors of shipments ofmedia. Administrators must manually notify offsite vendors of incomingmedia and manually request offsite vendors to send media back when thedata contained on the media no longer needs to be protected. Someoffsite vendors have proprietary interfaces to allow the administratorto electronically notify the vendor of incoming media or request media.However, the administrator must manually send the electronicnotification and must manually incorporate the information on incomingmedia into the media vaulting software. Overall, the management of mediavaulting may be a very time-intensive and manual process.

SUMMARY OF THE INVENTION

In one embodiment, a plurality of vaulting policies are created. Eachvaulting policy has one or more cycles that specify a movement of mediato a destination location and a time to execute the cycle. A firstvaulting policy is associated with a first set of media and a secondvaulting policy is associated with a second set of media that includes asubset of the first set of media. The second vaulting policy supersedesthe first vaulting policy for the media contained in the subset.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments in accordance with the invention areillustrated in the drawings in which:

FIG. 1 illustrates an exemplary configuration of a vaulting manager tomanage media vaulting;

FIG. 2 is a flow diagram illustrating an exemplary method for managingmedia vaulting that may be used by the vaulting manager of FIG. 1;

FIG. 3 illustrates an exemplary screen to configure vaulting policiesthat may be presented by the vaulting manager of FIG. 1;

FIG. 4 is a flow diagram illustrating an exemplary method for creatingmedia movement jobs that may be used by the vaulting manager of FIG. 1;

FIG. 5 is a flow diagram illustrating an exemplary method fordetermining a vaulting policy to apply;

FIG. 6 illustrates an exemplary presentation to a user of multiple mediamovement jobs;

FIG. 7 is a flow diagram illustrating an exemplary method fordetermining media to be removed from one or more backup devices for amedia movement job;

FIG. 8 illustrates an exemplary presentation to a user of media tounload;

FIG. 9 is a flow diagram illustrating an exemplary method for confirmingcompletion of a media movement job; and

FIG. 10 illustrates an exemplary user interface that may be used toverify completion of media movement for one or more media.

DETAILED DESCRIPTION

An exemplary configuration using a vaulting manager 100 to manage mediavaulting is illustrated in FIG. 1. It should be understood that that theterm media should not be regarded as being limited to two or more piecesof media, but could also include a single medium. The vaulting manager100 includes a plurality of vaulting policies 102. Each vaulting policy102 may include one or more cycles specifying a movement of media to adestination location and a time to execute the cycle. Vaulting policies102 and vaulting cycles will be described in further detail below.

In one embodiment, a portion of the media to be managed by vaultingmanager 100 may be media containing data written by a backup application110. Backup application 110 is responsible for backup jobs 112, 114 anduses backup device 130 to backup and restore data. By way of example,backup device 130 may be tape libraries, optical tape libraries,standalone tape drives, or other types of backup devices. The backupjobs 112, 114 may each be full or incremental backups of data containedin various locations, such as on a backup server executing the backupapplication 110, one or more clients communicatively coupled to thebackup server, or other location (e.g., disk device) storing data to bebacked up. In alternate embodiments, backup application 110 may beresponsible for a different number of backup jobs than that illustratedin FIG. 1 and may use a different number of backup devices to store andretrieve data.

After data has been written to backup application 110, at least aportion of the media are protected and vaulted according to one or morevaulting policies 102. Vaulting manager 100 may include an integrationagent 108 to receive backup job information for the backup jobs 112, 114from backup applications 110. By way of example, integration agent 108may receive backup job information from backup application 110 via acommunicative coupling (e.g., internet or intranet) between the backupapplication 110 and the vaulting manager 100 using an opencommunication, such as XML (Extensible Markup Language). Vaultingmanager 100 may manage media vaulting for media containing data writtenby more than one backup application and thus may be communicativelycoupled to additional backup applications.

The backup job information may include devices and/or media pools usedby the backup jobs, types of the backup jobs (e.g., full orincremental), locations of the data or systems being backed up by thebackup jobs, media used by a backup job, start and/or completion time ofthe backup job, and any other information that may be used by vaultingmanager 100 to manage media vaulting. The vaulting manager 100 may usethe time the data was written as a relative time period to execute theone or more cycles of a vaulting policy 102 associated with the media.In alternate embodiments, vaulting manager 100 may obtain informationneeded to manage the vaulting of media from a source other than backupapplication 110 and thus may not be communicatively coupled to anybackup applications and may not include integration agent 108.

In addition to vaulting policies 102, vaulting manager 100 may alsoinclude or have access to information (not shown) on media pools, backupjobs, systems backed up, individual media, current location of media,and/or other types of information that may be used to manage mediavaulting. Some of this information may have initially been obtained frombackup application 110 or may have been obtained from an alternatesource, such as from a user or other application. This information mayfacilitate the management of media vaulting in embodiments in whichvaulting manager 100 is additionally or alternately responsible formanaging media that has been previously vaulted or has been written byapplications to which vaulting manager is not communicatively coupled.As will be described in further detail below, the information may alsobe used to create media movement jobs based on the vaulting policies102.

In some embodiments, vaulting manager 100 may also include logic 104,communicatively coupled to the vaulting policies 102 and an integrationagent 108. Logic 104 may receive the backup job information fromintegration agent 108 and use this information, along with the vaultingpolicies 102, to create a media movement job. As will be described infurther detail below, the media movement job may include a destinationfor a set of media and a time period to perform the media movement.Logic 104 may also determine which vaulting policy 102 to apply to amedium based on a set membership of the medium.

Vaulting manager 100 may additionally include a user interface 106communicatively coupled to logic 104 and/or vaulting policies 102. Userinterface 106 may be used to receive and convey information to a user(e.g., an administrator or operator). By way of example, the userinterface 106 may be used to configure (add, edit, and delete) thevaulting policies 102 and to associate each of the vaulting policies 102to a set of media. As will be described in further detail below, userinterface 106 may also be used to receive confirmation verifyingcompletion of media movement.

Configurations different than the one shown in FIG. 1 may be used inalternate embodiments. For example, integration agent 108 mayadditionally or alternately reside on one or more of the serversexecuting the backup application 110. This configuration may facilitatethe exchange of information in configurations containing firewalls.Additionally, vaulting manager 100 may be a component of backupapplication 110.

Vaulting manager 100, logic 104, user interface 106, and integrationagent 108 may be implemented in software, firmware, hardware, or acombination of these. Additionally, these components may reside onseparate physical locations, such as separate servers. By way ofexample, in one embodiment, the user interface 106 may be a web browseron a remote client.

FIG. 2 illustrates an exemplary method of managing media vaulting thatmay be used by vaulting manager 100. A plurality of vaulting policies102 are created 205. By way of example, the vaulting policies 102 may becreated by a user using user interface 106. Each vaulting policy 102 mayinclude a policy name and a time period to protect data associated withthe vaulting policy 102. In one embodiment, after the time period hasexpired, the media storing the protected data may be destroyed orrecycled as scratch media. In another embodiment, the media may not bedestroyed or recycled until both the time period has expired and thebackup application using the media reports that the media is no longerprotected. In alternate embodiments, the vaulting policy may not includea time period and the media may be destroyed or recycled when the backupapplication using the media reports that the media is no longerprotected.

For each vaulting policy 102, one or more cycles are also created 210.Each cycle specifies a movement of media to a destination location and atime to execute the cycle. Destination locations may include adestination site and may be specific locations within that site or maybe a general location type (e.g., backup device, onsite vault, oroffsite vault). The time to execute the cycle may be a relative time(e.g., number of days or hours) after data is written to a media. By wayof example, media associated with a cycle having a relative time of 0days may be executed the day data is written to the media. In alternateembodiments, absolute times or times relative to one or more previousmovements of the media may also be used.

FIG. 3 illustrates an exemplary screen 300 that may be presented by userinterface 106 to create vaulting cycles 210 for a vaulting policy 102. Adisplay area 302 may be included to display the vaulting policy 102 forwhich the cycles are being created. The screen 300 may also include asecond display area 304 to display the minimum protection time frame fordata associated with the vaulting policy 102. In alternate embodiments,screen 300 may not include display areas 302, 304 or may alternatelyinclude entry areas for the user to create the vaulting policy 102 usingscreen 300 instead of a separate screen.

Screen 300 further includes a column 306 for displaying a time toexecute the cycle. As previously described, in one embodiment, the timemay be a relative number of hours or days after data has been written tomedia. A second column 308 displays the destination for a movement ofmedia associated with the vaulting policy 102 and a third column 310displays the site location of the destination. A button 312 may beprovided to add a new cycle and a second button 314 may be provided toedit existing cycles. Alternately, columns 306, 308, 310 may be editedand/or added to in-place.

The policy illustrated in FIG. 3 is configured to move media on the dayit is written to device located at Site 1. Some media may already belocated in device. Seven days afterwards, a second cycle specifies themedia should be moved to an onsite vault also located at Site 1. Thirtydays after the media is written, it is moved to an offsite vault locatedat Site 2. In some embodiments, an automatic media movement may occurforty-five days after the media is written, returning the media to abackup device and recycling the media as scratch media.

Returning to FIG. 2, after media policies and cycles are created 205,210, some or all of the vaulting policies 102 may each be associated 215to one or more sets of media. A set of media may contain one or moremedia. By way of example, sets of media may be media contained in amedia pool, media used for a specified backup job, media used to backupa specified system, and an individual medium. In one embodiment,vaulting policies 102 may be hierarchical. With hierarchical vaultingpolicies 102, a first set of media may be associated to a first vaultingpolicy and a second set of media that includes a subset of the first setof media may be associated to a second vaulting policy. For mediacontained in the subset, the second vaulting policy supersedes the firstvaulting policy.

In one embodiment, a hierarchical order may be: 1) media pool; 2) backupjob; 3) system from which data originated; and 4) individual medium. Inthis hierarchy, a policy applied to a lower order in the hierarchysupersedes policies applied in a higher order. For example, if a firstvaulting policy is applied to media in a first media pool and a secondvaulting policy is applied to media used by a first backup job, thesecond vaulting policy supersedes the first vaulting policy for mediathat is in the first media pool and was used by the first backup job.Hierarchies other than the illustrated hierarchy may also be used.

In some embodiments, media movement jobs may be created by logic 104based on cycles specified in the vaulting policies 102. Each mediamovement job may include a destination for a subset of media and a timeperiod to perform the media movement. By way of example, the time periodmay include a start time to start the media movement job and a due timeto complete the media movement job. The start time may be determinedbased on a user parameter specifying days or times to execute a vaultingcycle and the due time may be calculated based on parameters specifyingestimated completion times for moving media from one location to anotherlocation. As media movement jobs may only be created at periodic times,media movements for some cycles may be delayed (i.e., may be createdlater than the execution time specified in the cycle).

Media movement jobs may be created for subsets of media located in asingle source location. Alternately, media movement jobs may be createdfor multiple source locations having a single destination. In someembodiments, the specific location within a destination (e.g., specificvault, or device) may be determined by logic 104 based on free spaces inthe specific location. In some embodiments, a single media movement jobmay be based on one or more than one vaulting policy 102.

FIG. 4 illustrates an exemplary method that may be used to create 400one or more media movement jobs. Backup job information may be obtained405 from a backup application 110 for one or more backup jobs 112, 114.As previously described, backup job information may include devicesand/or media pools used by the backup jobs, types of the backup jobs(e.g., full or incremental), locations of the data or systems beingbacked up by the backup jobs, media used by a backup job, start and/orcompletion time of the backup job, and any other information that may beused by vaulting manager 100 to manage media vaulting. Media movementjobs may be created for all cycles of a vaulting policy 102 at the timethe backup job information is obtained. Alternately, vaulting manager100 may store some or all of the backup job information (e.g., date themedia was written) to create future media movements specified byvaulting cycles. In alternate embodiments, information needed for thecreation of media movement jobs may be obtained in an alternate fashionthan that described

Next, logic 104 may use the backup job information to determine 410 themedia used by the backup jobs 112, 114. Any media that has been writtenmay need to be moved, or may start a time period running for a mediamovement job, according to a cycle specified in a vaulting policy 102.Thus, one or more vaulting policies 102 may be applied 415 to the mediaused by backup jobs 112, 114. By way of example, a media movement jobmay be created for the second cycle of Policy8 302 with a destination ofOnsite Vault in Site 1 with a start time of seven days after the mediaassociated with Policy8 has been used.

In addition to the creation of media movement jobs specified by cyclesof vaulting policies 102, logic 104 may also create media movement jobsfor media containing data that has exceeded the protection date. Asprotection for this data is no longer required, the media may berecycled and used as scratch media for subsequent executions of backupjobs 112, 114. Accordingly, media movement jobs may be created to returnthe media to a backup device 130 or a site containing backup devices.

In some embodiments, logic 104 may use additional constraints in thecreation of media movement jobs. By way of example, one or more vaultingpolicies 102 may specify that a lockable container must be used whensending media to an offsite vendor. Therefore, a media movement job mayfirst be created moving media to a lockable container and thensubsequent jobs may be created for the shipment of the container to theoffsite vendor.

In some embodiments, vaulting manager 100 may be communicatively coupledto other vaulting managers. In these embodiments, vaulting manager 100may remotely initiate media movement jobs on vaulting managers indifferent source and destination locations. After a media movement jobhas been created 400, vaulting manager 100 may automatically create oneor more media movement jobs on vaulting managers located at one or moresource locations of the media for the parent media movement job createdat 400. This media movement job notifies operators at the source site tolocate the media and ship it. Similarly, vaulting manager 100 may alsoautomatically create a media movement job at the vaulting managerlocated at the destination location for the parent media movement job,which may provide notification to the destination of the incoming media.To prevent the inclusion of media that was not shipped to thedestination (e.g., because the media is missing), vaulting manager 100may wait to create the media movement job for the destination site untilafter the source site has completed its media movement job.

In addition to or instead of the coupling to other vaulting managers,vaulting manager 100 may also include an electronic interface (e.g.,FTP) to one or more software applications used by third parties, such asoffsite vendors. Vaulting manager 100 may use the electronic interfaceto automatically notify the third party of incoming media or requestthat media be returned. This automatic notification may be done bycreating media movement jobs at the source and/or destination locationsin a manner similar to that described above. Alternately, the electronicnotification may be sent in accordance with requirements of the thirdparty software.

In some embodiments, vaulting policies 102 may be hierarchical, whereina specific vaulting policy for a subset of media may supersede avaulting policy for a larger set. FIG. 5 illustrates an exemplary methodthat may be used to determine 500 which vaulting policy 102 to apply toa medium that has been used 410 by a backup job 112,114 in ahierarchical scheme.

First, a determination is made as to whether a vaulting policy 102exists 510 for the medium (i.e., a vaulting policy 102 has beenassociated to the medium). If a vaulting policy 102 exists for themedium, the vaulting policy 102 associated with the medium is applied515. Otherwise, a determination is made as to whether a vaulting policy102 exists 520 for the system the medium was used to back up. If such avaulting policy exists 420, the vaulting policy 102 associated with thesystem is applied 525.

If a vaulting policy 102 for the system does not exist, but a vaultingpolicy 102 exists 530 for the backup job 112, 114 that used the medium,that policy is applied 535. Otherwise, if a vaulting policy 102 exists540 for the media pool containing the medium, the vaulting policy 102associated with the media pool is applied 545. If there are no vaultingpolicies 102 associated with the medium, system, backup job, and mediapool, the method ends 550. Alternately, a default vaulting policy 102may be applied.

FIG. 6 illustrates an exemplary screen 600 that may be presented by userinterface 106 listing media movement jobs to be performed. The mediamovement jobs may be listed for a particular site or may include allmedia movement jobs initiated by vaulting manger 100. A first column 610may be provided to list a job identification number.

The start time for the media movement job may be listed in a secondcolumn 620. A third column may also be provided to list the destination630. In some embodiments, media movement jobs may be created forspecific locations within a site. In those embodiments, the destinationmay be a combination of destination site and specific location withinthe device. Alternately, an additional column may be provided to listthe specific location within a site for the media movement job.

The screen further includes a fourth column 640 specifying the due timefor completion of the media movement. The due time may have beencalculated by logic 104 based on parameters estimating times to movemedia between locations and the current location of the media. A scrollbar 650 may also be provided on screen 600, as the list of mediamovement jobs may be lengthy.

As illustrated by FIG. 7, in some embodiments, logic 104 mayadditionally determine 705 a list of media to be removed from one ormore backup devices 130 to perform a media movement job. The list maythen be presented 710 to a user (e.g., media operator). In addition, orin the alternative, the media to be removed may be automaticallyunloaded by sending a request to a backup application 110 to unload themedia or sending a request directly to the backup device 130 or othersoftware managing the backup device 130.

FIG. 8 illustrates an exemplary presentation to a user, which may beprovided by user interface 106, of a list of media to be removed. Asshown in the screen 800, the list may include a column 810 for the mediato be removed. A second column 820 is also provided listing the devicecontaining the media and a third column 830 may be provided specifyingthe location of the device. Scroll bar 840 may also be provided tofacilitate the viewing of the list.

The location may be a data center within a site and may also include agrid location of the device. In one embodiment, the list may be orderedbased on the location of the device. For example, the first device anoperator unloads is listed first and the remaining devices are listed inorder based on the physical proximity of the devices to the firstdevice. The information needed to order the list may be obtained from auser via user interface 106 or may be retrieved from another location.

FIG. 9 illustrates an exemplary method that may be used to confirmcompletion of a media movement job for one or more media. After a mediamovement job is created 400, confirmation may be received 905 from auser verifying completion of the media movement job for one or moremedia. FIG. 10 illustrates an exemplary screen 1000 that may be providedby user interface 106 for the user to verify completion of a mediamovement job.

Display areas 1002, 1004 may be provided to list the job ID and thedestination for the media movement job. Screen 1000 further includes atext entry area 1006 to enter the media which have reached thedestination of the media movement job. The user interface 106 mayreceive this information, for example, from a keyboard or a barcodescanner used to scan barcodes located on the media. A verify button 1016may be provided to verify that the media movement job has been completedfor each piece of media entered in text entry area 1006. Alternately,the verify button 1016 may verify multiple pieces of time.

Screen 1000 may also include a first column 1008 to list the pendingmedia for the media movement job and a second column 1010 listing thelocation of the media. Scroll bar 1012 may be used to scroll the list ofpending media. A third column 1014 may list the media which have beenverified. In alternate embodiments, buttons may be provided to movemedia from the pending media list to the verified media list.

Returning to FIG. 9, after receiving 905 confirmation verifyingcompletion of the media movement job for one or more media, logic 104may determine 910 one or more missing media that did not complete themedia movement. The missing media may be reported to a user (e.g., usinguser interface 106). Additional information, such as the last knownlocation of the media and/or the user last verifying completion of aprevious media movement job may also be provided. In alternateembodiments, 910 may not be performed.

It should be appreciated that the methods described above may beperformed by hardware components or may be embodied in sequences ofmachine-executable instructions, which may be used to cause a machine,such as a general-purpose or special-purpose processor or logic circuitsprogrammed with the instructions to perform the actions set forth inFIGS. 2, 4, 5, 7, and 9. Alternatively, the methods may be performed bya combination of hardware and software. It should also be appreciatedthat the methods may be performed in an order different than thatdescribed above. Further, steps or sequences may be added or removedwithout departing from the scope and spirit of embodiments in accordancewith the invention.

1. A method comprising: creating a plurality of vaulting policies, eachvaulting policy having one or more cycles specifying a movement of mediato a destination location and a time to execute the cycle; associating afirst vaulting policy of the plurality to a first set of media; andassociating a second vaulting policy of the plurality to a second set ofmedia, the second set of media comprising a subset of the first set ofmedia, the second vaulting policy superseding the first vaulting policyfor the media contained in the subset.
 2. The method of claim 1, whereinthe first set consists of media contained in a media pool.
 3. The methodof claim 2, wherein second set consists of media containing data for abackup job.
 4. The method of claim 2, wherein the second set consists ofmedia containing data for a system.
 5. The method of claim 2, whereinthe second set consists of a medium in the media pool.
 6. The method ofclaim 1, further comprising creating a media movement job based on atleast the first vaulting policy, the media movement job comprising adestination for a second subset of media in the set and a time period toperform the media movement.
 7. The method of claim 6, wherein creating amedia movement job comprises: obtaining backup job information from abackup application for one or more backup jobs; and determining at leasta portion of the second subset of media by determining media used by theone or more backup jobs.
 8. The method of claim 6, further comprisingreceiving a confirmation verifying completion of the media movement jobfor one or more media of the second subset.
 9. The method of claim 8,further comprising determining one or more missing media based on theconfirmation.
 10. The method of claim 6, wherein the time periodcomprises a start time to start the media movement job and a due time tocomplete the media movement job.
 11. The method of claim 6, furthercomprising creating a second media movement job based on the mediamovement job, the second media movement job created on a vaultingmanager at a source location of at least a portion of the second subsetof media.
 12. The method of claim 6, further comprising creating asecond media movement job based on the media movement job, the secondmedia movement job created on a vaulting manager at the destination forthe second subset of media.
 13. The method of claim 1, wherein the timefor each of the one or more cycles comprises a relative number of daysafter data is written to a medium.
 14. The method of claim 1, whereincreating a plurality of vaulting policies comprises for each vaultingpolicy, setting a time period for protecting data.
 15. The method ofclaim 1, wherein each of the destination locations for the one or morecycles comprises one of a backup device, an onsite vault, and an offsitevault.
 16. A method comprising: receiving backup job information from abackup application for one or more backup jobs; and creating a mediamovement job for a set of media based on the backup job information andone or more vaulting policies, the media movement job comprising adestination for a set of media and a time period to perform the mediamovement.
 17. The method of claim 16, wherein creating the mediamovement job comprises: determining media used by the one or more backupjobs based on the backup job information; and applying the one or morevaulting policies to at least a portion of the media used by the one ormore backup jobs.
 18. The method of claim 16, wherein the time periodcomprises a start time to start the media movement job and a due time tocomplete the media movement job.
 19. The method of claim 16, furthercomprising: determining media to be removed from a backup deviceassociated with the backup application based on the media movement job;presenting to a user a list of the media to be removed from the backupdevice.
 20. A system comprising: a plurality of vaulting policies, eachvaulting policy having one or more cycles specifying a movement of mediato a destination location and a time to execute the cycle; and a userinterface to configure the plurality of vaulting policies and toassociate each of the vaulting policies to a set of media.
 21. Thesystem of claim 20, further comprising logic, communicatively coupled tothe vaulting policies, to determine a vaulting policy of the pluralityof vaulting policies to apply to a medium based on a set membership ofthe medium, wherein a vaulting policy for a subset supersedes a vaultingpolicy for a set.
 22. The system of claim 21, further comprising: anintegration agent to receive backup job information for a plurality ofbackup jobs from a backup application; and wherein said logic is furtherto create a media movement job based on at least one of the plurality ofvaulting policies and the backup job information, the media movement jobcomprising a destination for a first set of media and a time period toperform the media movement.
 23. The system of claim 21, wherein saiduser interface is further configured to receive a confirmation for themedia movement job specifying completion of the media movement job forone or more media in the first set.
 24. The system of claim 21, furthercomprising vaulting information comprising a current location of one ormore media.
 25. At least one machine-readable medium having storedthereon sequences of instructions, which, when executed by a machine,cause the machine to perform the actions: creating a plurality ofvaulting polices, each vaulting policy having one or more cyclesspecifying a movement of media to a destination location and a time toexecute the cycle; associating a first vaulting policy of the pluralityto a first set of media; and associating a second vaulting policy of theplurality to a second set of media, the second set of media comprising asubset of the first set of media, the second vaulting policy supersedingthe first vaulting policy for the media contained in the subset.
 26. Themedium of claim 25, further comprising instructions, which when executedby the machine, cause the machine to perform the action creating a mediamovement job based on at least the first vaulting policy, the mediamovement job including a destination for a second subset of media in thefirst set and a time period to perform the media movement.
 27. Themedium of claim 25, further comprising instructions, which when executedby the machine, cause the machine to perform the action of receiving aconfirmation verifying completion of the media movement job for one ormore media in the second subset.